DRUID 8.8

Deployment Dates

The table below lists the deployment date of DRUID v8.8 across DRUID Clouds. To view the DRUID Releases Calendar, see Druid ChatBot Releases.

Druid Cloud Community

*.community.Druidplatform.com

Druid Cloud US

*.us.Druidplatform.com

Druid Cloud Australia

*au.Druidplatform.com

Druid Cloud West-Europe (PROD)

*.Druidplatform.com

January 16, 2025 February 13, 2025 February 13, 2025 February 13, 2025

These release notes give you a brief, high-level description of the improvements implemented to existing features.

If you have questions about your DRUID tenant, please contact support@Druidai.com or your local DRUID partner for more information.

Connector Host Upgrade Recommended!  This release includes features that require upgrade of your DRUID Connector Host:
  • Custom Code improvement

Improvements

  • WhatsApp channels - receiving audio messages. The bot now supports processing voice messages in WhatsApp channels by leveraging the native Voice (MS Cognitive Service) channel. For more information, see WhatsApp Meta Channel or WhatsApp Vonage Channel.
  • Note:  The bot will respond to voice messages with text only.
  • NLU Evaluation - Tenant timezone in Conversation History export. The Conversation History export now converts Date UTC to the tenant's timezone (if set) for improved accuracy.
  • Megabots - Manual handling of megabot affinity. This release introduces the ability to manually control which child bot the megabot engages. You can now specify the child bot using [[ChatUser]].PredictTargetBot during the Intent rephrase flow, eliminating the need for role usage on bots or within the conversations. Additionally, you can restrict predictions to specific child bots with [[ChatUser]].RestrictedTargetBots. To return to the default behavior, simply set these values to null. For more information, see Megabots.
  • Custom Code - read and write txt and JSON files. DRUID now supports reading content from TXT and JSON files, as well as generating new files in these formats. These files can be shared with users during a chat interaction or sent to third-party systems via API calls. This functionality is particularly useful for scenarios where data needs to be extracted from files or dynamically generated and forwarded to external systems. For more information, see Custom Code.